Greptile Summary

This PR fixes SSH exit-status propagation in the PAM proxy by splitting the single bidirectional error channel into two separate done channels (clientToServerDone / serverToClientDone), explicitly calling serverChannel.CloseWrite() when the client-to-server direction finishes (signalling EOF to the remote process so it delivers its exit-status), and raising the serverReqDone window from 500 ms to 3 s. The two remaining findings are both P2 style suggestions around goroutine lifecycle clarity and cumulative teardown latency.

Confidence Score: 5/5

Safe to merge; the fix is logically sound with no P0/P1 defects — only minor style and latency observations remain.

All findings are P2. No goroutine leaks, no data-loss paths, and no security issues introduced. The two style comments concern goroutine lifecycle explicitness and potential teardown latency, neither of which blocks correctness.

No files require special attention.

Important Files Changed

_{Reviews (1): Last reviewed commit: "fix status code propagation" | Re-trigger Greptile}